-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DRAFT EXPLORATION] chore(NA): upgrade to webpack 5 #191106
Draft
mistic
wants to merge
205
commits into
elastic:main
Choose a base branch
from
mistic:upgrade-to-webpack-5
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
## Summary Upgrades references to webpack5 from v5.91.0 to v5.96.1 A v4 to v5 upgrade is being explored here: elastic#191106 --------- Co-authored-by: kibanamachine <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
## Summary Combine some Renovate groups. Disable TS group. Closes elastic#189415. Disable Webpack group until elastic#191106 is finished.
…upgrade-to-webpack-5
…ing on ui-shared-deps-npm and src
…vices/theme/warning on ui-shared-deps-npm and src"" This reverts commit 0ed6f7a.
mistic
force-pushed
the
upgrade-to-webpack-5
branch
from
December 29, 2024 04:40
d529c35
to
09ac9af
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:all-open
Backport to all branches that could still receive a release
chore
ci:build-webpack-bundle-analyzer
release_note:skip
Skip the PR/issue when compiling release notes
Team:Operations
Team label for Operations Team
v9.0.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP
Summary
TODO
@kbn/optimizer-webpack-helpers
to support webpack v5data.plugin.chunk.0.js
/ci
and make sure we get our first green CI, otherwise work on the errors until we donode scripts/build_kibana_platform_plugins --no-cache
).--openssl-legacy-provider
flagsNodePolyfillPlugin
(here) and add each polyfill needed individually per each webpack config to check if we get smaller bundles. If we do it's better to go with the case by case need approach instead of deploying a bunch of polyfills with NodePolyfillPlugin. As another alternative, create a custom smaller plugin with only the union of all needed polyfills.resourceQuery: { not: /raw/ }
is not necessary on other webpack configs like storybook one__kbnBootstrap__
can't be found